-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Conversation
Hmm maven failed in CI - that should be unrelated to this PR. |
If we have this PR merged, do we still need the Julia doc build pipeline in Jenkins? |
@mxnet-label-bot add [Julia, Doc] |
I think having a separate test for the docs package like Julia is a good idea and wish we had that for each kind, like C++ docs, Scala, etc. With this PR, it is duplicating the test, but this was the easiest way and keeps all of the docs generated in the same pipeline as the website output. Let's leave it in there for now. Make sure everything is working how we want it, (docs are being built!) then discuss further how things should work, and try to streamline. |
It seemed to be something to do with the the |
It did it twice now already. This new test is the third attempt. |
@iblis17 There's a line in the ubuntu setup guide that says "The MXNet package for Julia is hosted in a separate repository, MXNet.jl, which is available on GitHub." But this isn't true anymore is it? |
@aaronmarkham It isn't true anymore. |
Thanks, I'll change that and rebase so maybe this CI/maven problem will be fixed. How far should the Julia docs go back? I could trigger the build in 1.4.x or earlier in For this PR though, I'd trigger whatever is compatible plus maybe note what's going on there if people browse the older versions. |
@iblis17 I tried to add some more details on getting Ubuntu configured natively (since all I did here was get it working via Docker and to run the docs), but I ran into this:
I saw a post that you might need to add this to the registry like this, but it didn't work:
|
|
||
```bash | ||
export MXNET_HOME=/<path to>/libmxnet | ||
wget -qO julia-10.tar.gz https://julialang-s3.julialang.org/bin/linux/x64/1.0/julia-1.0.3-linux-x86_64.tar.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am using CI's Julia setup as a guide.
https://github.com/apache/incubator-mxnet/blob/master/ci/docker/install/ubuntu_julia.sh
julia -e 'using InteractiveUtils; versioninfo()' | ||
``` | ||
|
||
#### Setup Your MXNet-Julia Environment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These steps come from CI's runtime_functions.sh:
https://github.com/apache/incubator-mxnet/blob/master/ci/docker/runtime_functions.sh#L1059-L1073
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you paste the preview link?
It's in the main description: |
BTW, Julia v1.0.4 is out. Let's test it: #15502. |
LGTM! Verified Julia installation and doc building process on an Ubuntu EC2 instance. |
Nice work! @aaronmarkham |
Description
Since the dmlc.ml domain is gone we lost our Julia docs (and other things).
This PR adds Julia docs to our regular website deployment pipeline. 💥 Links to the Julia docs will no longer go to a spam/malware website.
Fixes #15415
Update: It also adds a thorough Ubuntu setup guide for Julia. The existing one doesn't work. However, this needs more eyes and testing. I did get it to work, but after a ton of troubleshooting, so I might have missed some env var or some setting that is required.
Update 2: I removed the separate Julia pipeline for docs. I needed to have its installation and config steps and it was duplicating things anyways. So since I had to fix CI, I went ahead and removed the duplication. That being said, sometime in the future it would be nice to revamp the docs build and have stages for each of the doc sets and make it so you don't have to rerun every stage of CI if one particular part of docs generation fails.
Preview
The Julia docs site ends up in /site in the Julia API area.
http://34.201.8.176/versions/julia/api/julia/site/index.html